Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0444

reference: 190-tree-1
name: 0444
tree-preservation-order: undefined
190-tpo-1
uprn
address-text
point: POINT (-0.940824 50.862450)
geometry: MULTIPOLYGON (((-0.940796 50.862447,-0.940797 50.862452,-0.940801 50.862457,-0.940807 50.862461,-0.940815 50.862464,-0.940824 50.862465,-0.940841 50.862462,-0.940847 50.862458,-0.940851 50.862453,-0.940853 50.862447,-0.940852 50.862441,-0.940848 50.862436,-0.940842 50.862432,-0.940825 50.862429,-0.940808 50.862432,-0.940802 50.862436,-0.940798 50.862441,-0.940796 50.862447)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL